Bad Memory On The Ids-4250-Xl; Blocking - Cisco IDS-4230-FE - Intrusion Detection Sys Fast Ethernet Sensor Installation And Configuration Manual

Troubleshooting the 4200 Series Appliance
Step 2

Bad Memory on the IDS-4250-XL

Step 3

Blocking

Cisco Intrusion Detection System Appliance and Module Installation and Configuration Guide Version 4.1
B-18
Running the SensorApp in single processor mode is the preferred
Note
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.
Turn off EventAction log and use CapturePacket True instead in the stream-based
signatures.
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
faulty memory.
Display events since a specified time for a specified alert level:
sensor# show events alert
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.
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:
Verify that NAC is running.
1.
See Verifying NAC is Running, page
Verify that NAC is connecting to the network devices.
2.
See Verifying NAC is Connecting, page
for the procedure for checking the IDS-4250-XL for
level hh:mm month day year
B-19, for the procedure.
B-20, for the procedure.
Appendix B Troubleshooting
78-15597-02