-
Cisco Traffic Anomaly Detector Module Configuration Guide (Software Version 6.0)
-
Index
-
Preface
-
Product Overview
-
Configuring the Detector Module on the Supervisor Engine
-
Initializing the Detector Module
-
Configuring the Detector
-
Configuring Zones
-
Configuring Zone Filters
-
Configuring Policy Templates and Policies
-
Learning the Zone Traffic Characteristics
-
Detecting Zone Traffic Anomalies
-
Using Interactive Detect Mode
-
Using Attack Reports
-
Using Detector Module Diagnostics Tools
-
Performing Maintenance Tasks
-
Feedback
Table Of Contents
Using Detector Module Diagnostic Tools
Displaying the Installed Software Version Number and License Agreement
Displaying the Software License Key Information
Displaying the Detector Module Configuration
Displaying Detector Module Zones
Using Counters to Analyze Traffic
Displaying Counters and Average Traffic Rates
Clearing Detector Module and Zone Counters
Monitoring Network Traffic and Extracting Attack Signatures
Configuring the Detector Module to Automatically Record Traffic
Activating the Detector Module to Manually Record Traffic
Stopping the Detector Module from Manually Recording Traffic
Displaying Manual Packet-Dump Settings
Exporting Packet-Dump Capture Files Automatically
Exporting Packet-Dump Capture Files Manually
Importing Packet-Dump Capture Files
Displaying Packet-Dump Capture Files
Generating Attack Signatures from Packet-Dump Capture Files
Copying Packet-Dump Capture Files
Deleting Packet-Dump Capture Files
Displaying General Diagnostic Data
Displaying the CPU Utilization
Using Detector Module Diagnostic Tools
This chapter describes how to display statistics and diagnostics on the Cisco Traffic Anomaly Detector Module (Detector module).
Note
Operational and configuration differences exist between a Detector module operating at 1 Gbps and a Detector module operating at 2 Gbps. This chapter discusses the differences between the 1-Gbps operation and the 2-Gbps operation. Unless stated, the information in this chapter applies to both modes of operation. For more information, see the "Understanding the 1-Gbps and 2-Gbps Bandwidth Options" section on page 1-6.
This chapter contains the following sections:
•
•
•
•
•
•
•
•
•
•
•
•
Displaying the Installed Software Version Number and License Agreement
You can display the software licensing agreement and the version number of the software image loaded on your Detector module. Viewing the version number allows you to verify which of the following bandwidth options your Detector module is using:
•
•
Note
To display the software version number and licensing agreement information, use the following command:
show version
Displaying the Software License Key Information
If the Detector module is using the XG version of the software image for 2-Gbps operation, you can display information related to the license key required to activate the XG software image. Display the license key information to verify the following information:
•
•
Note
To display the software version number and licensing agreement information, use the following command:
show license-key
Displaying the Detector Module Configuration
You can display the Detector module configuration file, which includes information about the Detector module configuration, such as interface IP addresses, default gateway addresses, and configured zones.
To display the Detector module configuration file, use the following command:
show running-config [all | detector | interfaces [interface-name] | zones]
Table 12-1 provides the arguments and keywords for the show running-config command.
The following example shows how to display the Detector module configuration file:
user@DETECTOR# show running-config detectorThe configuration file consists of the commands that you enter to configure the Detector module with the current settings. You can export the Detector module configuration file to a remote FTP server for backup purposes or for implementing the Detector module configuration parameters on another Detector module. See the "Displaying Detector Module Zones" section for more information.
Displaying Detector Module Zones
You can display an overview of the zones to see which zones are active and what their current status is by entering the show command in global mode.
Table 12-2 describes the possible operating states of a zone.
The following example shows how to display an overview of the Detector module zones:
user@DETECTOR# showUsing Counters to Analyze Traffic
You can display Detector module and zone counters to display information on the current traffic that the Detector module is handling, analyze zone traffic, and perform monitoring tasks.
This section contains the following topics:
•
•
Displaying Counters and Average Traffic Rates
To display the zone counters, use one of the following commands:
•
•
•
•
•
•
To display the Detector module counters, use the command in global or configuration mode.
To display the zone counters, use the command in one of the following command modes:
•
•
The rate units are in bits per second (bps) and in packets per second (pps).
Note
The counter units are in packets and in kilobits. The counters are set to zero when you activate zone detection.
Table 12-3 displays the Detector module counters.
The following example shows how to display the Detector module average traffic rates:
user@DETECTOR-conf-zone-scannet# show ratesClearing Detector Module and Zone Counters
You can clear the Detector module or zone counters if you are going to perform testing and want to be sure that the counters include information from the testing session only. The Detector module clears the counters and the average traffic rates.
To clear the Detector module counters, use the following command in global or configuration mode:
clear counters
The following example shows how to clear the Detector module counters:
user@DETECTOR-conf# clear countersTo clear the zone counters, use one of the following commands:
•
•
The following example shows how to clear the zone counters:
user@DETECTOR-conf-zone-scannet# clear countersDisplaying the Zone Status
To display an overview of the zone and its current status, use the show command in zone configuration mode. The overview includes the following information:
•
•
See the "Configuring Zone Attributes" section on page 5-6 for more information.
•
See the "Configuring Flex-Content Filters" section on page 6-2 and the "Configuring Dynamic Filters" section on page 6-12 for more information.
•
See the "Using Counters to Analyze Traffic" section for more information.
The following example shows how to display the zone status:
user@DETECTOR-conf-zone-scannet# showManaging Detector Module Logs
The Detector module automatically logs the system activity and events. You can display the Detector module logs to review and track the Detector module activity.
Table 12-4 displays the event log levels.
The log file displays all log levels (emergencies, alerts, critical, errors, warnings, notification, informational, and debugging). The Detector module log file includes zone events with severity levels: emergencies, alerts, critical, errors, warnings, and notifications.
You can display the event log locally or from a remote server. This section contains the following topics:
Managing Online Event Logs
This section describes how to manage the Detector module real-time logging of events and contains the following topics:
Displaying Online Event Logs
You can activate the Detector module monitoring feature and display a real-time event log, which enables you to view the online logging of the Detector module events. To display the online event logs, use the following command:
event monitor
The following example shows how to activate monitoring:
user@DETECTOR# event monitorThe screen constantly updates to show new events.
Note
Exporting Online Event Logs
You can export the Detector module online event logs to display the Detector module operations that are registered in the log file and to display the Detector module events from a remote host while they are registered in the Detector module log file. The Detector module log file is exported using the syslog mechanism. You can export the Detector module log file to several syslog servers and specify additional servers so that if one server goes offline, another server is available to receive messages.
Online Detector module log export is applicable with a remote syslog server only. If a remote syslog server is not available, use the copy log command to export the Detector module log information to a file.
The following is an example of a logging event:
Sep 11 16:34:40 10.4.4.4 cm: scannet, 5 threshold-tuning-start: Zone activation completed successfully.The system log message syntax is as follows:
event-date event-time Detector-IP-address software-daemon/module zone-name event-severity-level event-type event-description
To export online event logs, perform the following steps:
Step 1
logging {facility | trap}Table 12-5 provides the keywords for the logging command.
Note
Step 2
logging host remote-syslog-server-ip
The remote-syslog-server-ip argument specifies the remote syslog server IP address.
To build a list of syslog servers that receive logging messages, use the logging host command more than once.
The following example shows how to configure the Detector module to send traps with a severity level that is higher than notification. The Detector module sends the traps using the facility local3 to a syslog server with IP address 10.0.0.191:
user@DETECTOR-conf# logging facility local3user@DETECTOR-conf# logging trap notificationsuser@DETECTOR-conf# logging host 10.0.0.191To display the configuration that the Detector module uses to export online event logs, use the show logging command or the show log export-ip command.
Managing the Log File
This section describes how to manage the Detector module log file and contains the following topics:
Displaying the Log File
You can display the Detector module log for diagnostic or monitoring purposes. The Detector module log file includes zone events with these severity levels: emergencies, alerts, critical, errors, warnings, and notification.
To display the Detector module log, use the following command in global mode:
show log
The following example shows how to display the Detector module log:
user@DETECTOR# show logYou can display a zone log to display events that relate to the specified zone only.
To display the zone log, use the show log command in zone configuration mode.
Exporting the Log File
You can export the Detector module log file to a network server for monitoring or diagnostics by entering one of the following commands in global mode:
•
•
Table 12-6 provides the arguments and keywords for the copy log ftp command.
Note
Because Secure File Transfer Protocol (SFTP) and Secure Copy Protocol (SCP) rely on Secure Shell (SSH) for secure communication, if you do not configure the key that the Detector module uses before you enter the copy command with the sftp or scp option, the Detector module prompts you for the password. See the "Configuring the Keys for SFTP and SCP Connections" section on page 4-24 for more information about how to configure the key that the Detector module uses for secure communication.
The following example shows how to export the Detector module log file to an FTP server:
user@DETECTOR# copy log ftp 10.0.0.191 log.txt <user> <password>Clearing the Log File
You can clear the Detector module or zone log file if it is large or if you are going to perform testing and want to be sure that the log file includes information from the testing session only.
To clear the zone log file of all entries, use the following command in zone configuration mode:
clear log
To clear the Detector module or zone log file of all entries, use the following command in configuration mode:
clear [zone zone-name] log
The optional zone zone-name keyword and argument specifies the zone name. The default is to clear the Detector module log file.
The following example shows how to clear the Detector module log:
user@DETECTOR-conf# clear logMonitoring Network Traffic and Extracting Attack Signatures
You can configure the Detector module to record traffic directly from the network through nonintrusive taps and create a database from the recorded traffic. By querying the recorded traffic database, you can analyze past events, generate signatures of an attack, or compare current network traffic patterns with traffic patterns that the Detector module recorded previously under normal traffic conditions.
You can configure filters so that the Detector module records only traffic that meets certain criteria or you can record all traffic data and filter the traffic that the Detector module displays.
The Detector module records the traffic in PCAP format, which is compressed and encoded by the gzip (GNU zip) program with an accompanying file in Extensible Markup Language (XML) format that describes the recorded data.
The Detector module can analyze the recorded traffic to determine if there are any common patterns or signatures that appear in the payload of the recorded attack packets. The Detector module can extract signatures from the recorded traffic. Using the signature, you can configure a flex-content filter to block all traffic containing packet payloads that match the signature.
The Detector module can record traffic as follows:
•
New packet-dump capture files replace the previous ones. To save previous packet-dump capture files, you must export them to a network server.
•
New packet-dump capture files replace previous files. To save the recorded traffic, export the packet-dump capture files to a network server before you activate the Detector module to record traffic again.
You can activate only one manual packet-dump capture at a time for a zone, but you can activate the manual packet-dump capture and the automatic packet-dump capture simultaneously. The Detector module can manually record traffic for up to four zones simultaneously.
The Detector module allocates, by default, 20-MB disk space for manual packet-dump capture files of all zones. The Detector module can save up to 80-MB disk space for manual and automatic packet-dump capture files of all zones. You must delete old files to free the disk space for additional packet-dump capture files.
This section contains the following topics:
•
•
•
•
•
•
•
•
•
•
•
Configuring the Detector Module to Automatically Record Traffic
You can activate the Detector module to automatically record network traffic for troubleshooting network problems or analyzing attack traffic. By using packet-dump capture filters, you can configure the Detector module to record only the traffic that meets the criteria that you specify. You can also record all traffic and apply packet-dump capture filters to the recorded traffic when you view it.
The Detector module records traffic in a capture buffer. When the capture buffer size reaches 50 MB, or after 10 minutes have elapsed, the Detector module saves the buffered information to a local file in a compressed format, clears the buffer, and then continues recording traffic.
The Detector module saves multiple automatic packet-dump capture files. The Detector module divides the recorded traffic based on the way that it handled the traffic, so you might have more than one automatic packet-dump capture file from a single time frame. The name of the automatic packet-dump capture file provides information about when the Detector module recorded the traffic and how it handled the traffic.
Table 12-7 describes the sections of the automatic packet-dump capture filename.
The Detector module saves one packet-dump capture file from the learning process and the following two types of packet-dump capture files when zone protection is enabled:
•
•
When you activate zone detection or activate the Detector module to automatically record network traffic, the Detector module erases all previous packet-dump capture files that it recorded during the detection process and creates new ones.
To configure the Detector module to automatically record network traffic, perform the following steps:
Step 1
packet-dump auto-captureStep 2
See the "Exporting Packet-Dump Capture Files Automatically" section.
The following example shows how to configure the Detector module to automatically record zone traffic:
user@DETECTOR-conf-zone-scannet# packet-dump auto-captureTo stop the Detector module from automatically capturing zone traffic data, use the no packet-dump auto-capture command.
To display the current packet-dump settings, use the show packet-dump command.
Activating the Detector Module to Manually Record Traffic
You can activate the Detector module to start recording traffic so that you can record traffic during a specific period or change the criteria that the Detector module uses to record the traffic.
The Detector module stops recording traffic and saves the manual packet-dump capture to a file when the specified number of packets have been recorded or when either the learning process or zone detection have ended.
You can activate only one manual packet-dump capture at a time for a zone, but you can activate the manual packet-dump capture and the automatic packet-dump capture simultaneously. The Detector module can record manual packet-dump captures for up to 10 zones simultaneously.
To activate a manual packet-dump capture, use the following command in zone configuration mode:
packet-dump capture [view] capture-name pdump-rate pdump-count [tcpdump-expression]
Note
Table 12-8 provides the arguments and keywords for the packet-dump command.
Table 12-8 Arguments and Keywords for the packet-dump Command
(Optional) Displays the traffic that the Detector module is recording in real time.
Name of the packet-dump capture file. Enter an alphanumeric string from 1 to 63 characters. The string can contain underscores but cannot contain spaces.
Sample rate in packet per seconds. Enter a value from 1 to 10000.
Note
A packet-dump capture configured with a high sample-rate value consumes resources. We recommend that you use high-rate values cautiously because of the potential performance penalty.
Number of packets to record. When the Detector module finishes recording the specified number of packets, it saves the manual packet-dump capture buffer to a file. Enter an integer from 1 to 5000.
(Optional) Filter that you apply to specify the traffic to record. The Detector module captures only traffic that complies with the filter expression. The expression rules are identical to the flex-content filter TCPDump expression rules. See the "Configuring the tcpdump-expression Syntax" section on page 6-5 for more information.
The following example shows how to activate a manual packet-dump capture to record 1000 packets with a sample rate of 10 pps and display the packets that are captured:
user@DETECTOR-conf-zone-scannet# packet-dump capture view 10 1000Stopping the Detector Module from Manually Recording Traffic
The Detector module stops a manual packet-dump capture when it records the number of packets that you specified when you activated the capture. However, you can stop a manual packet-dump capture before the Detector module records the specified number of packets by performing one of the following actions:
•
•
no packet-dump capture capture-name
The capture-name argument specifies the name of the capture to stop.
The Detector module saves the packet-dump capture file.
Displaying Manual Packet-Dump Settings
You can display the current amount of disk space that the Detector module allocated for manual packet-dump capture files by using the show packet-dump command in configuration mode or in global mode. The Detector module allocates a single block of disk space for the manual packet-dump capture files of all zones.
The following example shows how to display the current amount of disk space that the Detector module allocated for manual packet-dump capture files:
user@DETECTOR-conf# show packet-dumpTable 12-9 describes the fields in the show packet-dump command output.
Exporting Packet-Dump Capture Files Automatically
You can configure the Detector module to automatically export packet-dump capture files to a network server that uses FTP, SFTP, or SCP to transfer files. When you enable the automatic export function, the Detector module exports the packet-dump capture files each time that it saves the contents of the packet-dump buffer to a local file. The Detector module exports the packet-dump capture files in PCAP format, which is compressed and encoded by the gzip (GNU zip) program, with an accompanying file in XML format that describes the recorded data. The XML schema is described in the Capture.xsd file which you can download from the Software Center at http://www.cisco.com/public/sw-center/.
To configure the Detector module to export packet-dump capture files automatically, use the following command in configuration mode:
export packet-dump file-server-name
The file-server-name argument specifies the name of a network server to which you export the files that you configure by using the file-server command. If you configure the network server for SFTP or SCP, you must configure the SSH key that the Detector module uses for SFTP and SCP communication. See the "Exporting Files Automatically to a Network Server" section on page 13-6 for more information.
The following example shows how to automatically export packet-dump capture files:
user@DETECTOR-conf# export packet-dump Corp-FTP-ServerExporting Packet-Dump Capture Files Manually
You can manually export packet-dump capture files to a network server that uses FTP, SFTP, or SCP to transfer files. You can export a single packet-dump capture file or all packet-dump capture files of a specific zone. The Detector module exports the packet-dump capture files in PCAP format, which is compressed and encoded by the gzip (GNU zip) program with an accompanying file in XML format that describes the recorded data. See the Capture.xsd file that accompanies the version for a description of the XML schema. You can download the xsd files that accompany the version from www.cisco.com.
To manually export packet-dump capture files to a network server, use one of the following commands in global mode:
•
•
•
Table 12-10 provides the arguments and keywords for the copy zone packet-dump command.
Table 12-10 Arguments and Keywords for the copy zone packet-dump Command
zone zone-name
Specifies the name of an existing zone.
packet-dump captures
Exports packet-dump capture files.
capture-name
(Optional) Name of an existing packet-dump capture file. If you do not specify the name of a packet-dump capture file, the Detector module exports all the zone packet-dump capture files. See the "Displaying Packet-Dump Capture Files" section for more information.
ftp
Specifies FTP.
sftp
Specifies SFTP.
scp
Specifies SCP.
server
IP address of the network server. Enter the IP address in dotted-decimal notation (for example, enter 192.168.10.2).
remote-path
Complete name of the path where the Detector module saves the packet-dump capture files.
login
(Optional) Server login name. The login argument is optional when you define an FTP server. When you do not enter a login name, the FTP server assumes an anonymous login and does not prompt you for a password.
password
(Optional) Password for the remote FTP server. If you do not enter the password, the Detector module prompts you for one.
file-server-name
Name of a network server. You must configure the network server using the file-server command.
If you configured the network server using SFTP or SCP, you must configure the SSH key that the Detector module uses for SFTP and SCP communication.
See the "Exporting Files Automatically to a Network Server" section on page 13-6 for more information.
Because SFTP and SCP rely on SSH for secure communication, if you do not configure the key that the Detector module uses before you enter the copy command with the sftp or scp option, the Detector module prompts you for the password. See the "Configuring the Keys for SFTP and SCP Connections" section on page 4-24 for more information about how to configure the key that the Detector module uses for secure communication.
The following example shows how to manually export the packet-dump capture files of zone scannet to FTP server 10.0.0.191:
user@DETECTOR# copy zone scannet packet-dump captures ftp 10.0.0.191 <user> <password>The following example shows how to manually export the packet-dump capture files of zone scannet to a network server that was defined by using the file-server command:
user@DETECTOR# copy zone scannet packet-dump captures cap-5-10-05 Corp-FTP-ServerImporting Packet-Dump Capture Files
You can import packet-dump capture files from a network server to the Detector module so that you can analyze past events or compare current network traffic patterns with traffic patterns that the Detector module previously recorded under normal traffic conditions. The Detector module imports the packet-dump capture files in both XML and PCAP formats.
To import a packet-dump capture file, use one of the following commands in global mode:
•
•
•
Table 12-11 provides the arguments and keywords for the copy zone packet-dump command.
Table 12-11 Arguments and Keywords for the copy zone packet-dump Command
ftp
Specifies FTP.
sftp
Specifies SFTP.
scp
Specifies SCP.
zone zone-name
Specifies the name of an existing zone for which the packet-dump capture files are imported.
packet-dump captures
Imports packet-dump capture files.
server
IP address of the network server. Enter the IP address in dotted-decimal notation (for example, enter 192.168.10.2).
full-file-name
Complete path and filename, excluding the file extension, of the file to import. If you do not specify a path, the server copies the file from your home directory.
Note
login
(Optional) Server login name. The login argument is optional when you define an FTP server. When you do not enter a login name, the FTP server assumes an anonymous login and does not prompt you for a password.
password
(Optional) Password for the FTP server. If you do not enter the password, the Detector module prompts you for one.
file-server-name
Name of a network server. You must configure the network server using the file-server command.
If you configured the network server using SFTP or SCP, you must configure the SSH key that the Detector module uses for SFTP and SCP communication.
See the "Exporting Files Automatically to a Network Server" section on page 13-6 for more information.
capture-name
Name of the file to import. The Detector module appends the name of the file to the path that you defined for the network server by using the file-server command.
Because SFTP and SCP rely on SSH for secure communication, if you do not configure the key that the Detector module uses before you enter the copy command with the sftp or scp option, the Detector module prompts you for the password. See the "Configuring the Keys for SFTP and SCP Connections" section on page 4-24 for more information about how to configure the key that the Detector module uses for secure communication.
The following example shows how to import packet-dump capture files of zone scannet from FTP server 10.0.0.191:
user@DETECTOR# copy ftp zone scannet packet-dump captures 10.0.0.191 /root/scannet/captures/capture-1 <user> <password>The following example shows how to import a packet-dump capture file from a network server:
user@DETECTOR# copy CorpFTP running-config capture-1Displaying Packet-Dump Capture Files
You can display either a list of packet-dump capture files or the contents of a single packet-dump capture file. By default, the Detector module displays a list of all zone packet-dump capture files.
To display packet-dump capture files, use the following command in zone configuration mode:
show packet-dump captures [capture-name [tcpdump-expression]]
Table 12-12 provides the arguments for the show packet-dump captures command.
Table 12-12 Arguments for the show packet-dump captures Command
capture-name
(Optional) Name of an existing packet-dump capture file. If you do not specify the name of a packet-dump capture file, the Detector module displays a list of all zone packet-dump capture files. See Table 12-13 for field descriptions of the command output. If you specify the name of a packet-dump capture file, the Detector module displays the file in TCPDump format.
tcpdump-
expression(Optional) Filter that the Detector module uses when displaying the packet-dump capture file. The Detector module displays only the portion of the packet-dump capture file that matches the filter criteria. The expression rules are identical to the flex-content filter TCPDump expression rules (see the "Configuring the tcpdump-expression Syntax" section on page 6-5).
The following example shows how to display the list of packet-dump capture files:
user@DETECTOR-conf-zone-scannet# show packet-dump capturesTable 12-13 describes the fields in the show packet-dump captures command output.
Table 12-13 Field Descriptions for the show packet-dump captures Command Output
Field
Capture-name
Name of the packet-dump capture file. See Table 12-7 for a description of the automatic packet-dump capture filenames.
Size (MB)
Size of the packet-dump capture file in megabytes.
Filter
User-defined filter that the Detector module used when recording traffic. The filter is in TCPDump format. The expression rules are identical to the flex-content filter TCPDump expression rules. See the "Configuring the tcpdump-expression Syntax" section on page 6-5 for more information.
Generating Attack Signatures from Packet-Dump Capture Files
An attack signature describes the common pattern that appears in the payload of attack packets. You can activate the Detector module to generate the signature of attack traffic and then use this information to quickly identify future attacks of the same type. This feature allows you to detect new DDoS attacks and Internet worms even before signatures are published (for example, from antivirus software companies or mailing lists).
The Detector module can generate an attack signature using the flex-content filter pattern expression syntax. You can use the attack signature in the flex-content filter pattern to filter out attack traffic. See the "Configuring Flex-Content Filters" section on page 6-2 for more information.
When you execute the attack signature generating process, you can determine the accuracy of the generated attack signature by specifying a reference packet-dump capture file containing clean (legitimate) traffic. After the Detector generates the attack signature from the packet-dump capture file containing malicious traffic, the Detector runs an analysis to determine how often the attack signature appears in the clean traffic of the reference packet-dump capture file. The Detector displays the results of the analysis as a percentage of the attack signature occurrences in the reference packet-dump capture file to the number of packets in the reference file. A percentage value that is less than 10% indicates that the attack signature is accurate and that you can use the signature to detect malicious traffic.
A percentage value that is greater than 10% indicates that the signature generating process failed. Do not use the signature to detect malicious traffic because it will result in the Detector wrongly identifying clean traffic as malicious traffic. The signature generating process may fail for the following reasons:
•
•
To generate a signature of an attack, perform the following steps:
Step 1
See the "Activating the Detector Module to Manually Record Traffic" section for more information.
Step 2
See the "Displaying Packet-Dump Capture Files" section for more information.
Step 3
show packet-dump signatures capture-name [reference-capture-name]Table 12-14 provides the arguments for the show packet-dump signatures command.
Table 12-15 describes the fields in the show packet-dump signatures command output.
Table 12-15 Field Descriptions for the show packet-dump signatures Command Output
Start Offset
Offset (in bytes) from the beginning of the packet payload where the pattern begins. If you copy the pattern into the flex-content filter pattern expression, copy this offset into the flex-content filter start-offset argument.
End Offset
Offset (in bytes) from the beginning of the packet payload where the pattern ends. If you copy the pattern into the flex-content filter pattern expression, copy this offset into the flex-content filter end-offset argument.
Pattern
Signature that the Detector module generated. The Detector module generates the signature using the flex-content filter pattern expression syntax. See the "Configuring the pattern-expression Syntax" section on page 6-8 for more information. You can copy this pattern into the flex-content filter pattern expression.
Percentage
Percentage of the attack signature occurrences in the reference packet-dump capture file to the number of packets in the reference file.
The following example shows how to generate a signature from a manual packet-dump capture file:
user@DETECTOR-conf-zone-scannet# show packet-dump signatures PDumpCaptureCopying Packet-Dump Capture Files
You can copy a packet-dump capture file (or a portion of a file) under a new name. When you copy an automatic packet-dump capture file or a manual packet-dump capture file, the Detector module saves them as manual files. If you want to save an existing automatic packet-dump capture file, you need to create a copy of it before the Detector module overwrites the automatic packet-dump capture file with a new one.
You must manually delete packet-dump capture files if you need to free disk space. See the "Deleting Packet-Dump Capture Files" section for more information.
To copy a packet-dump capture file, use the following command in configuration mode:
copy zone zone-name packet-dump captures capture-name [tcpdump-expression] new-name
Table 12-16 provides the arguments and keywords for the copy zone packet-dump captures command.
Table 12-16 Arguments and Keywords for the copy zone packet-dump captures Command
zone zone-name
Specifies the name of an existing zone.
packet-dump
Copies the packet-dump capture file.
captures capture-name
Specifies the name of an existing packet-dump capture file.
tcpdump-expression
(Optional) Filter that the Detector module uses to copy the packet-dump capture file. The Detector module copies only the portion of the packet-dump capture file that matches the filter criteria. The expression rules are identical to the flex-content filter TCPDump expression rules. See the "Configuring the tcpdump-expression Syntax" section on page 6-5 for more information.
new-name
Name of the new packet-dump capture file.
The name is an alphanumeric string from 1 to 63 characters and can contain underscores but cannot contain spaces.
The following example shows how to copy a portion of the packet-dump capture file capture-1 that complies with the capture file under the name capture-2:
user@DETECTOR-conf# copy zone scannet capture-1 "tcp and dst port 80 and not src port 1000" capture-2Deleting Packet-Dump Capture Files
The Detector module allocates by default 20 MB of disk space for manual packet-dump capture files of all zones. It can save up to 80 MB of manual and automatic packet-dump capture files of all zones. To free disk space for additional packet-dump capture files, delete the old ones.
You can save only one manual packet-dump capture file per zone and no more than 10 packet-dump capture files on the Detector module. You must delete old manual packet-dump capture files to allow space for new files.
To delete automatic or manual packet-dump capture files, use one of the following commands:
•
•
Table 12-17 provides the arguments and keywords for the clear packet-dump command.
The following example shows how to delete all manual packet-dump capture files:
user@DETECTOR-conf# clear packet-dump captures *Displaying General Diagnostic Data
You can display a general summary of the diagnostic data by using the following command:
show diagnostic-info [details]
The diagnostic data consists of the following information:
•
•
•
•
•
•
•
•
Note
•
•
Note
Displaying Flash Memory Usage
The Detector module maintains activity logs and zone attack reports. If the disk usage is higher than 75 percent, or if a large number of zones is defined on the Detector module (over 500), we recommend that you decrease the file history parameters. When the used disk space reaches approximately 80 percent of the disk maximum capacity, the Detector module displays a warning message in its syslog.
If the Detector module displays a warning message, you can export the zone attack reports to a network server and then delete the old attack reports (see the "Exporting Attack Reports" section on page 11-6 and the "Deleting Attack Reports" section on page 11-9).
We recommend that you periodically store the Detector module records on a network server, and then clear the logs.
Note
You can display the available flash over the amount of flash installed on the Detector module by using the following command in global mode:
show flash-usage
The following example shows how to display flash memory usage:
user@DETECTOR# show flash-usage2%Displaying Memory Consumption
The Detector module displays the following information:
•
•
The anomaly detection engine memory usage is affected by the number of active zones and the number of services that each zone monitors.
Note
To display the Detector module memory consumption, use the following command:
show memory
The following example shows how to display the Detector module memory consumption:
user@DETECTOR# show memorytotal used free shared buffers cachedIn KBytes: 2065188 146260 1918928 0 2360 69232Anomaly detection engine used memory: 0.3%
Note
Displaying the CPU Utilization
The Detector module displays the percentage of CPU time in user mode, system mode, niced tasks (tasks with a nice value, which represents the priority of a process, that is negative), and idle. Niced tasks are counted in both system time and user time, so the total CPU utilization can be more than 100 percent.
To display the current percentage of CPU utilization, use the following command:
show cpu
The following example shows how to display the current percentage of CPU utilization:
user@DETECTOR# show cpuHost CPU1: 0.0% user, 0.1% system, 0.1% nice, 98.0% idleMonitoring System Resources
You can display an overview of the resources that the Detector module is using to help you analyze and monitor the system status by entering the following command in global or configuration mode:
show resources
The following example shows how to display the system resources:
user@DETECTOR# show resourcesTable 12-18 describes the fields in the show resources command output.
Table 12-18 Field Descriptions for the show resources Command Output
Host CPU1
Percentage of CPU time for CPU1 in user mode, system mode, niced tasks (tasks with a nice value, which represents the priority of a process, that is negative), and idle. Niced tasks are also counted in system time and user time so that the total CPU utilization can be more than 100 percent.
Flash space usage
Percentage of the allocated flash space that the Detector module is using.
When the flash space usage reaches approximately 75 percent of the flash maximum capacity, the Detector module displays a warning message in its syslog and sends a trap.
Note
We recommend that you periodically store the Detector module records on a network server and delete the old records.
Flash space usage (continued)
If the flash space usage reaches 80 percent, you can export the zone attack reports to a network server and then delete the old attack reports (see the "Exporting Attack Reports" section on page 11-6 and the "Deleting Attack Reports" section on page 11-9).
Accelerator card memory usage
Percentage of memory that the accelerator card is using on a per-port basis: 1 port for 1-Gbps operation; 2 ports for 2-Gbps operation.
If the accelerator card memory usage is higher than 85 percent, the Detector module generates an SNMP trap. A high value may indicate that the Detector module is monitoring a high volume of traffic.
Accelerator card CPU utilization
Percentage of the accelerator card CPU that is being utilized on a per-port basis: 1 port for 1-Gbps operation; 2 ports for 2-Gbps operation.
If the accelerator card CPU utilization is higher than 85 percent, the Detector module generates an SNMP trap. A high value may indicate that the Detector module is monitoring a high volume of traffic.
Anomaly detection engine used memory
Specifies the percentage of memory that the Detector module statistical engine uses. The anomaly detection engine memory usage is affected by the number of active zones, the number of services each of the zones monitors, and the amount of nonspoofed traffic that the Detector module is monitoring.
If the anomaly detection engine memory usage is higher than 90 percent, we strongly recommend that you lower the number of active zones.
Dynamic filters used
Total number of dynamic filters that are active in all the zones. The Detector module displays the number of active dynamic filters and the percentage of dynamic filters that are active out of the total number of dynamic filters that the Detector module supports, which is 150,000. If the number of active dynamic filters reaches 150,000, the Detector module generates an SNMP trap with a severity level of EMERGENCY. If the number of active dynamic filters reaches 135,000, the Detector module generates an SNMP trap with a severity level of WARNING.
A high value may indicate that the Detector module is monitoring a high traffic volume of a DDoS attack.
For more information about the SNMP traps that the Detector module generates, see Table 4-14 on page 4-27.
Managing the ARP Cache
You can display or manipulate the Address Resolution Protocol (ARP) cache to clear an address mapping entry or to manually define an address mapping entry. To manage the ARP cache, use the following command from the configuration mode:
arp {-a [arp_hostname] | -d arp_hostname | -n [arp_hostname] | -s arp_hostname hw_addr}
Table 12-19 provides the arguments and keywords for the arp command.
Caution
Displaying Network Statistics
You can display the host network connections, routing tables, interface statistics, and multicast memberships to debug network problems by entering one of the following commands:
netstat [address_family_options] [--tcp | -t] [--udp | -u] [--raw | -w] [--listening | -l] [--all | -a] [--numeric | -n] [--numeric-hosts] [--numeric-ports] [--numeric-users] [--symbolic | -N] [--extend | -e [--extend | -e]] [--timers | -o] [--program | -p] [--verbose | -v] [--continuous | -c] [delay]
netstat {--route | -r} [address_family_options] [--extend | -e [--extend | -e]] [--verbose | -v] [--numeric | -n] [--numeric-hosts] [--numeric-ports] [--numeric-users] [--continuous | -c] [delay]
netstat {--interfaces | -i} [iface] [--all | -a] [--extend | -e [--extend | -e]] [--verbose | -v] [--program | -p] [--numeric | -n] [--numeric-hosts] [--numeric-ports] [--numeric-users] [--continuous | -c] [delay]
netstat {--groups | -g} [--numeric | -n] [--numeric-hosts] [--numeric-ports] [--numeric-users] [--continuous | -c] [delay]
netstat {--masquerade | -M} [--extend | -e] [--numeric | -n] [--numeric-hosts] [--numeric-ports] [--numeric-users] [--continuous | -c] [delay]
netstat {--statistics | -s} [--tcp | -t] [--udp | -u] [--raw | -w] [delay]
netstat {--version | -V}
netstat {--help | -h}
Note
Table 12-20 provides arguments and keywords for the netstat command.
Note
Note
The following example shows how to display netstat information in verbose:
user@DETECTOR# netstat -vActive Internet connections (w/o servers)Proto Recv-Q Send-Q Local Address Foreign Address Statetcp 0 0 localhost:1111 localhost:32777 ESTABLISHEDtcp 0 0 localhost:8200 localhost:32772 ESTABLISHED...tcp 0 0 localhost:33464 localhost:8200 TIME_WAITtcp 1 0 localhost:1113 localhost:33194 CLOSE_WAIT...Active UNIX domain sockets (w/o servers)unix 2 [ ] STREAM CONNECTED 928unix 3 [ ] STREAM CONNECTED 890 /tmp/.zserv...user@DETECTOR#Using Traceroute
You can determine the route that packets take to arrive at a network host to debug network problems by entering the following command:
traceroute ip-address [-F] [-f first_ttl] [-g gateway] [-i iface]
[-m max_ttl] [-p port] [-q nqueries] [-s src_addr] [-t tos] [-w waittime] [packetlen]
Note
Table 12-21 provides the arguments and keywords for the traceroute command.
The following example shows how to trace the route to IP address 10.10.10.34:
user@DETECTOR# traceroute 10.10.10.34traceroute to 10.10.10.34 (10.10.10.34), 30 hops max, 38 byte packets1 10.10.10.34 (10.10.10.34) 0.577 ms 0.203 ms 0.149 msVerifying Connectivity
You can send ICMP ECHO_REQUEST packets to network hosts and verify connectivity by entering the following command:
ping ip-address [-c count] [-i interval] [-l preload] [-s packetsize] [-t ttl] [-w deadline] [-F flowlabel] [-I interface]
[-Q tos] [-T timestamp option] [-W timeout]Table 12-22 provides arguments and keywords for the ping command.
You can enter a maximum of 10 arguments and keywords in one command.
The following example shows how to send one ICMP ECHO_REQUEST packet to IP address 10.10.10.30:
user@DETECTOR# ping 10.10.10.30 -n 1Obtaining Debug Information
If the Detector module experiences an operational problem, Cisco TAC may request that you send them a copy of the Detector module internal debug information. The Detector module debug core file contains information for troubleshooting Detector module malfunctions. The file output is encrypted and intended for use by Cisco TAC personnel only.
To extract debug information to an FTP, SCP, or SFTP server, perform the following steps:
Step 1
See the "Displaying the Log File" section for more information.
Step 2
Step 3
copy debug-core time {ftp | scp | sftp} server full-file-name [login [password]]Table 12-23 provides the arguments and keywords for the copy debug-core command.
The following example shows how to extract debug information from November 9 at 06:45 a.m. of the current year to FTP server 10.0.0.191:
user@DETECTOR# copy debug-core 11090645 ftp 10.0.0.191 /home/debug/debug-file <user> <password>
