B-11
Cisco Intrusion Detection System Appliance and Module Installation and Configuration Guide Version 4.1
78-15597-02
Appendix B Troubleshooting
Troubleshooting the 4200 Series Appliance
To verify that the sensor in question does not have an IP address conflict with
another host on the network, follow these steps:
Step 1
Log in to the CLI.
Step 2
Determine whether the interface is up:
sensor# show interfaces
command-control is up
If the output says
command-control is down
, there is a hardware issue or an IP
address conflict. Go to Step 3.
Step 3
Make sure the sensor’s cabling is correct.
Refer to the chapter for your sensor in this hardware guide.
Step 4
Run the setup command to make sure the IP address is correct.
See
Initializing the Sensor, page 10-2
, for the procedure.
SensorApp and Alerting
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
Sensing Process Not Running
The sensing process (SensorApp) should always be running. If it is not, you do
not receive any alerts.
Содержание IDS-4230-FE - Intrusion Detection Sys Fast Ethernet Sensor
Страница 4: ......
Страница 450: ...Appendix B Troubleshooting ...