Filter
Top Products
C-29
Cisco Intrusion Prevention System Sensor CLI Configuration Guide for IPS 7.2
OL-29168-01
Appendix C Troubleshooting
Troubleshooting the Appliance
AnalysisEngine V-2013_04_10_11_00_7_2_0_14 (Release) 2013-04-10T11:05:55-0500
Running
CollaborationApp V-2013_04_10_11_00_7_2_0_14 (Release) 2013-04-10T11:05:55-0500
Running
CLI V-2013_04_10_11_00_7_2_0_14 (Release) 2013-04-10T11:05:55-0500
Upgrade History:
IPS-K9-7.2-1-E4 11:17:07 UTC Thu Jan 10 2013
Recovery Partition Version 1.1 - 7.2(1)E4
Host Certificate Valid from: 17-Apr-2013 to 18-Apr-2015
sensor#
Step 3
If the Analysis Engine is not running, look for any errors connected to it.
sensor# show events error fatal past 13:00:00 | include AnalysisEngine
evError: eventId=1077219258696330005 severity=warning
originator:
hostId: sensor
appName: sensorApp
appInstanceId: 1045
time: 2004/02/19 19:34:20 2004/02/19 19:34:20 UTC
errorMessage: name=errUnclassified Generating new Analysis Engine configuration file.
Note
The date and time of the last restart is listed. In this example, the last restart was on 2-19-2004
at 7:34.
Step 4
If you do not have the latest software updates, download them from Cisco.com. Read the Readme that
accompanies the software upgrade for any known DDTS for the SensorApp or the Analysis Engine.
Step 5
If the Analysis Engine is still not running, enter
show tech-support
and save the output.
Step 6
Reboot the sensor.
Step 7
Enter
show version
after the sensor has stabilized to see if the issue is resolved.
Step 8
If the Analysis Engine still reads
Not Running
, contact TAC with the original show tech support
command output.
For More Information
•
For more information on IPS system architecture, see Chapter A, “System Architecture.”
•
For the procedure for obtaining the latest Cisco IPS software, see Obtaining Cisco IPS Software,
page 20-1.