12-20-2006 01:14 AM - edited 03-11-2019 02:11 AM
This is the output when the proccesor was high. Some of the VPN client users were unable to log in. when those users that were logged in started getting out the proccessor activity started going down until it reached 7%.
12-26-2006 12:36 PM
What version of software are you using in the pix ?
12-26-2006 11:29 PM
The version is 7.0. PIX 515E
12-27-2006 08:06 AM
Mate,
How many VPN users were logged in? Does your PIX have a VPN accelerator card (is it Unrestricted PIX)?
If you don't have any VPN termination capacity problems then you might need to check your IP Audit logs (if you have configured it). If you don't have it configured I would suggest that you do that on all physical interfaces and set the action to "log" only rather than "block" and then you can monitor if there is any malicious activities from any source.
Hope this helps ...
Cheers.
12-27-2006 08:20 AM
Check for incoming icmp log from hosts configured on the pix. Could be
- a misconfigured server the pix cannot reach
- a patch not well applied on syslog-server or snmp-server.
- misconfgured pix eg wrong ip server-address,
- port udp/514 not opened on server, etc...
Check either the syslog-server and snmp-server.
As a permanent workaround, enable icmp echo and icmp echo reply for the faulty host.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide
Subject | Author | Posted | |
---|---|---|---|
04-24-2025 08:55 PM | |||
05-03-2024 02:42 PM | |||
10-24-2012 05:40 AM | |||
04-23-2025 05:42 PM | |||
05-10-2016 02:20 AM |