Cisco 4215 - Intrusion Detection Sys Sensor Configuration Manual page 435

Appendix C Troubleshooting
To make sure AnalysisEngine is running, follow these steps:
Log in to the CLI.
Step 1
Determine the status of the AnalysisEngine service:
Step 2
sensor# show version
Application Partition:
Cisco Intrusion Prevention System, Version 5.0(1)S149.0
OS Version 2.4.26-IDS-smp-bigphys
Platform: AIP-SSM-20
Serial Number: 021
No license present
Sensor up-time is 19 days.
Using 505495552 out of 1984704512 bytes of available memory (25% usage)
system is using 17.3M out of 29.0M bytes of available disk space (59% usage)
application-data is using 37.7M out of 166.6M bytes of available disk space (24% usage)
boot is using 40.5M out of 68.5M bytes of available disk space (62% usage)
MainApp
AnalysisEngine
CLI
Upgrade History:
IDS-K9-maj-5.0-1-
Recovery Partition Version 1.1 - 5.0(1)S149
sensor#
If the AnalysisEngine is not running, look for any errors connected to it:
Step 3
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
Step 4 Make sure you have the latest software updates:
sensor# show version
Upgrade History:
IDS-K9-maj-5.0-1-
Recovery Partition Version 1.1 - 5.0(1)S149
78-16527-01
2005_Mar_04_14.23
2005_Mar_04_14.23
2005_Mar_04_14.23
14:16:00 UTC Thu Mar 04 2004
The date and time of the last restart is listed. In this example, the last restart was on 2-19-2004
at 7:34.
14:16:00 UTC Thu Mar 04 2004
Cisco Intrusion Prevention System Sensor CLI Configuration Guide for IPS 5.0
Troubleshooting the 4200 Series Appliance
(Release) 2005-03-04T14:35:11-0600
(Release) 2005-03-04T14:35:11-0600
(Release) 2005-03-04T14:35:11-0600
Running
Not Running
C-9