Appendix B Troubleshooting
Troubleshooting the 4200 Series Appliance
B-18
Cisco Intrusion Detection System Appliance and Module Installation and Configuration Guide Version 4.1
78-15597-02
Note
Running the SensorApp in single processor mode is the preferred
workaround. You should use this workaround unless you see
Signature 993 missed packet alarms after you apply the workaround.
If you do, go to Step 2.
Step 2
Turn off EventAction log and use CapturePacket True instead in the stream-based
signatures.
Bad Memory on the IDS-4250-XL
Some IDS-4250-XLs were shipped with faulty DIMMs on the XL cards. The
faulty DIMMs cause the sensor to hang or SensorApp to stop functioning and
generate a core file.
See the
Partner Field 52563
for the procedure for checking the IDS-4250-XL for
faulty memory.
Step 3
Display events since a specified time for a specified alert level:
sensor# show events alert
level hh:mm month day year
For example, show events alert high 10:00 September 22 2002 displays all high
severity events since 10:00 a.m. September 22, 2002.
Events from the specified time are displayed.
Blocking
After you have configured NAC, you can verify if NAC is running properly by
using the show version command. To verify that NAC is connecting to the
network devices, use the show statistics networkAccess command.
To troubleshoot NAC, follow these steps:
1.
Verify that NAC is running.
See
Verifying NAC is Running, page B-19
, for the procedure.
2.
Verify that NAC is connecting to the network devices.
See
Verifying NAC is Connecting, page B-20
, for the procedure.
Summary of Contents for IDS-4230-FE - Intrusion Detection Sys Fast Ethernet Sensor
Page 4: ......
Page 450: ...Appendix B Troubleshooting ...