E-29
Cisco Intrusion Prevention System Appliance Hardware Installation Guide for IPS 7.1
OL-24002-01
Appendix E Troubleshooting
Troubleshooting the Appliance
Total Packets Transmitted = 219260
Total Bytes Transmitted = 103668610
Total Transmit Errors = 0
Total Transmit FIFO Overruns = 0
sensor#
Step 3 Make sure the sensor cabling is correct.
Step 4 Make sure the IP address is correct.
For More Information
• To make sure the sensor cabling is correct, refer to the chapter for your sensor in this document.
• For the procedure for making sure the IP address is correct, refer to Configuring Network Settings.
The SensorApp and Alerting
This section helps you troubleshoot issues with the SensorApp and alerting. It contains the following
topics:
• The SensorApp Is Not Running, page E-29
• Physical Connectivity, SPAN, or VACL Port Issue, page E-31
• Unable to See Alerts, page E-32
• Sensor Not Seeing Packets, page E-34
• Cleaning Up a Corrupted SensorApp Configuration, page E-35
The SensorApp Is Not Running
The sensing process, SensorApp, should always be running. If it is not, you do not receive any alerts.
The SensorApp is part of the Analysis Engine, so you must make sure the Analysis Engine is running.
To make sure the Analysis Engine is running, follow these steps:
Step 1 Log in to the CLI.
Step 2 Determine the status of the Analysis Engine service and whether you have the latest software updates.
sensor# show version
Application Partition:
Cisco Intrusion Prevention System, Version 7.1(3)E4
Host:
Realm Keys key1.0
Signature Definition:
Signature Update S605.0 2011-10-25
OS Version: 2.6.29.1
Platform: ASA5585-SSP-IPS10
Serial Number: 123456789AB
No license present
Sensor up-time is 13 days.
Using 4395M out of 5839M bytes of available memory (75% usage)
system is using 26.2M out of 160.0M bytes of available disk space (16% usage)
application-data is using 69.7M out of 171.6M bytes of available disk space (43%
usage)
Comments to this Manuals