Sensorapp And Alerting; Sensorapp Not Running - Cisco IPS-4255-K9 - Intrusion Protection Sys 4255 Installation Manual

Troubleshooting the Appliance
Total Packets Transmitted = 219260
Total Bytes Transmitted = 103668610
Total Transmit Errors = 0
Total Transmit FIFO Overruns = 0
sensor#
If the output says the command and control interface link status is down, there is a hardware issue or an
IP address conflict.
Step 3 Make sure the sensor cabling is correct.
Make sure the IP address is correct.
Step 4
For More Information
•
•

SensorApp and Alerting

This section helps you troubleshoot issues with SensorApp and alerting. It contains the following topics:
•
•
•
•
•

SensorApp Not Running

The sensing process, SensorApp, should always be running. If it is not, you do not receive any alerts.
SensorApp is part of Analysis Engine, so you must make sure the Analysis Engine is running. To make
sure Analysis Engine is running, follow these steps:
Log in to the CLI.
Step 1
Determine the status of the Analysis Engine service.
Step 2
sensor# show version
Application Partition:
Cisco Intrusion Prevention System, Version 7.0(1)E3
Host:
Signature Definition:
OS Version:
Platform:
Serial Number:
License expired:
Sensor up-time is 7 days.
Using 1018015744 out of 2093600768 bytes of available memory (48% usage)
Cisco Intrusion Prevention System Appliance and Module Installation Guide for IPS 7.0
A-30
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
SensorApp Not Running, page A-30
Physical Connectivity, SPAN, or VACL Port Issue, page A-32
Unable to See Alerts, page A-33
Sensor Not Seeing Packets, page A-35
Cleaning Up a Corrupted SensorApp Configuration, page A-37
Realm Keys key1.0
Signature Update S329.0
Virus Update V1.2
2.4.30-IDS-smp-bigphys
ASA-SSM-20
JAB0948035P
11-Apr-2008 UTC
Chapter A
Configuring Network Settings
2008-04-16
2005-11-24
Troubleshooting
.
OL-18504-01