Sensorapp And Alerting; Sensing Process Not Running - Cisco IDS-4230-FE - Intrusion Detection Sys Fast Ethernet Sensor Installation And Configuration Manual

Appendix B Troubleshooting
Step 1
Step 2
Step 3
Step 4

SensorApp and Alerting

Sensing Process Not Running

Cisco Intrusion Detection System Appliance and Module Installation and Configuration Guide Version 4.1
78-15597-02
To verify that the sensor in question does not have an IP address conflict with
another host on the network, follow these steps:
Log in to the CLI.
Determine whether the interface is up:
sensor# show interfaces
command-control is up
If the output says
command-control is down
address conflict. Go to Step 3.
Make sure the sensor's cabling is correct.
Refer to the chapter for your sensor in this hardware guide.
Run the setup command to make sure the IP address is correct.
See Initializing the Sensor, page
This section helps you troubleshoot issues with SensorApp and alerting.
This section contains the following topics:
• Sensing Process Not Running, page B-11
• Physical Connectivity, SPAN, or VACL Port Issue, page B-12
Unable to See Alerts, page B-14
•
• Sensor Not Seeing Packets, page B-15
Cleaning Up a Corrupted SensorApp Configuration, page B-16
•
Running SensorApp in Single CPU Mode, page B-17
•
• Bad Memory on the IDS-4250-XL, page B-18
The sensing process (SensorApp) should always be running. If it is not, you do
not receive any alerts.
Troubleshooting the 4200 Series Appliance
, there is a hardware issue or an IP
10-2, for the procedure.
B-11